home *** CD-ROM | disk | FTP | other *** search
- Path: seagoon.newcastle.edu.au!usenet
- From: mazz@faceng.newcastle.edu.au (Richard Mazzaferri)
- Newsgroups: comp.lang.c++
- Subject: Re: Idle curiosity: Delphi properties in C++
- Date: Thu, 18 Jan 1996 01:31:13 GMT
- Organization: Newcastle University
- Message-ID: <4dk4ch$680@seagoon.newcastle.edu.au>
- References: <4cm1hp$mok$1@canberra.DIALix.oz.au> <L0u7wg2yqzFJ083yn@iaccess.za> <4d6rbs$5uj2@tigger.cc.uic.edu>
- NNTP-Posting-Host: tesla.newcastle.edu.au
- X-Newsreader: Forte Agent .99a.107
-
- olczyk@sunphy1 (Thadeus Olczyk) wrote:
-
- > Units are simply compilation units. Any language that is meant to be used
- > for programs more then a thousand lines must have some version of units,
- > in C++ it is header/source file combinations.
- >
- > The dificulty in Delphi is that the interface and implementation parts
- > must be held in the same file. When files get large it makes them unweildly.
-
- The difficulty in C++ is that there is really no concept of a unit. Header
- files and source files are _not_ the same thing. This is a contributing
- factor to the reason why C++ compilation is _so_ slow compared to a decent
- Pascal compiler - none of the public declarations from a header file can be
- stored in compiled form in the compiled unit file because the header could
- be compiled differently next time using different preprocessor definitions.
- This can also lead to mismatches between the way a 'unit' was compiled and
- the way another 'unit' references the first, as every C/C++ programmer has
- probably experienced.
-
- Have fun,
- Mazz.
- mazz@faceng.newcastle.edu.au
-
-